Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1216

reference
111-tree-1
name
1216
tree-preservation-order

undefined

111-tpo-1
uprn
address-text
point
POINT (-1.011808 50.865502)
geometry
MULTIPOLYGON (((-1.011752 50.865496,-1.011754 50.865508,-1.011762 50.865518,-1.011774 50.865526,-1.011790 50.865531,-1.011808 50.865533,-1.011825 50.865531,-1.011841 50.865526,-1.011854 50.865518,-1.011862 50.865508,-1.011865 50.865497,-1.011863 50.865486,-1.011855 50.865476,-1.011842 50.865468,-1.011827 50.865463,-1.011809 50.865461,-1.011792 50.865462,-1.011776 50.865467,-1.011763 50.865475,-1.011755 50.865485,-1.011752 50.865496)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL